Secure and lightweight traffic forwarding systems and methods to cloud based network security systems

ABSTRACT

A method implemented by an agent operating on a mobile device communicating to a cloud-based system includes opening up local listening sockets on the mobile device; redirecting outgoing traffic from all application on the mobile device except the agent to the local listening sockets; and forwarding the outgoing traffic from the local listening sockets to the cloud-based system with additional information included therein for the cloud-based system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of co-pending U.S. patentapplication Ser. No. 14/461,790 filed Aug. 18, 2014, and entitled “OUTOF BAND END USER NOTIFICATION SYSTEMS AND METHODS FOR SECURITY EVENTSRELATED TO NON-BROWSER MOBILE APPLICATIONS” and U.S. patent applicationSer. No. 13/446,856 filed Apr. 13, 2012, and entitled “ARCHIVING SYSTEMSAND METHODS FOR CLOUD BASED SYSTEMS,” the contents of which areincorporated in full by reference herein.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to computer networking systemsand methods. More particularly, the present disclosure relates to secureand lightweight traffic forwarding mechanisms to cloud based networksecurity systems.

BACKGROUND OF THE DISCLOSURE

Conventional web and Domain Name System (DNS) cloud based networksecurity solutions have problems associated with traffic forwarding,user authentication, device validation, and application identificationon mobile operating systems. In the past, a majority of the web trafficwas generated by browser based applications that were compliant withHypertext Transfer Protocol (HTTP) protocol standards in its entirety.With the proliferation of mobile applications (“apps”),traffic-forwarding mechanisms have faced numerous challenges. Mobileapps are purposely built to talk to dedicated servers using mechanismsthat may not be proxy friendly, may not handle HTTP redirections or maynot support authentication cookies. Traditional browser based webtransactions have a user agent as a source identifier, but not allmobile apps support unique user agents. Similarly, a DNS request doesnot have any application or user authentication information. Solutionsother than proxy, such as those that incorporate Secure Sockets Layer(SSL) or Internet Protocol Security (IPsec) Virtual Private Network(VPN) as a traffic forwarding mechanism, can handle authentication forall traffic, but lack the scalability and computational efficiency asafforded by proxy based solutions. Further, conventional approaches donot provide a way for secure web gateways to identify a sourceapplication package and lack the capacity to enforce applicationspecific organizational policies, such as blocking social networkingapps. Additionally, conventional traffic forwarding solutions do notoffer a way to locally apply device specific policies, like bandwidthcontrol, that is beneficial to apply locally as request bytes going tocloud would cumulate from all devices. The conventional solutions alsooften lack the scalability and the ability required for supporting BYOD(bring your own device) model wherein only partial or containerizedtraffic is forwarded to a secure web gateway. Lastly, conventionalmethods do not offer the capacity to generate security notifications incase of locally defined device level policy violations and needre-routing to operating system specific push notification services.

BRIEF SUMMARY OF THE DISCLOSURE

In an exemplary embodiment, a method implemented by an agent operatingon a mobile device communicating to a cloud-based system includesopening up local listening sockets on the mobile device; redirectingoutgoing traffic from all application on the mobile device except theagent to the local listening sockets; and forwarding the outgoingtraffic from the local listening sockets to the cloud-based system withadditional information included therein for the cloud-based system. Thelocal listening sockets can be a Transmission Control Protocol (TCP)listening socket for Web traffic and a User Datagram Protocol (UDP)listening socket for Domain Name System (DNS) traffic. The redirectingoutgoing traffic can include using an Internet Protocol (IP) tables,firewall rules-based approach where the agent configures firewall rulesto reroute the outgoing traffic to the local listening sockets. Theredirecting outgoing traffic can include using a tunnel interfaceapproach using a tunnel interface to reroute the outgoing traffic to thelocal listening sockets. The method can further include applying localpolicies at the mobile device, through the agent, prior to forwardingthe outgoing traffic. The cloud-based system can be configured to applyremote policies subsequent to the forwarding the outgoing traffic. Themethod can further include blocking an outgoing request based on theoutgoing traffic based on the local policies and displaying a locallygenerated end user notification. The local policies can includebandwidth quota limits. The additional information can include any ofapp unique package name, app version, operating system version, devicemodel, and agent app version.

In another exemplary embodiment, a mobile device includes a networkinterface communicatively coupled to a network, a processorcommunicatively coupled to the network interface, and memory storinginstructions that when executed cause the processor to: open up locallistening sockets on the mobile device; redirect outgoing traffic fromall application on the mobile device except the agent to the locallistening sockets; and forward the outgoing traffic from the locallistening sockets to a cloud-based system with additional informationincluded therein for the cloud-based system.

In yet another exemplary embodiment, a cloud-based security systemincludes one or more cloud nodes communicatively coupled to a network;wherein each of the one or more cloud nodes is configured to: receiveoutgoing traffic from local listening sockets at a mobile device withadditional information included therein, wherein the outgoing traffic isreceived subsequent to having local policies applied at the mobiledevice; and apply remote policies on the outgoing traffic, wherein theoutgoing traffic is either Web traffic or Domain Name System (DNS)traffic from the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated and described herein withreference to the various drawings, in which like reference numbers areused to denote like system components/method steps, as appropriate, andin which:

FIG. 1 is a network diagram of a distributed security system, and thelike;

FIG. 2 is a network diagram of the distributed security system of FIG. 1illustrating various components in more detail;

FIG. 3 is a block diagram of a server which may be used in thedistributed security system of FIG. 1 or standalone;

FIG. 4 is a block diagram of a mobile device which may be used in thesystem of FIG. 1 or with any other cloud-based system;

FIG. 5A is a network diagram of a cloud system and FIG. 5B is a networkdiagram of a network with a distributed security cloud providing DNSaugmented security;

FIG. 6 is a network diagram of a network with a distributed securitycloud providing DNS augmented security;

FIG. 7 is a flow diagram of an archiving method;

FIG. 8 is a flowchart of an archiving method;

FIG. 9 is a network diagram of a network depicting an exemplaryoperation of the archiving methods of FIGS. 7 and 8;

FIG. 10 is a flow diagram of an out of band notification system andmethod;

FIG. 11 is a block diagram of a user interface (UI) for the out of bandnotification system of FIG. 10;

FIG. 12 is a screen shot of an exemplary out-of-band notification on amobile device;

FIG. 13 is a network diagram of a secure and lightweight tunnelconfiguration between a mobile device and a cloud system;

FIG. 14 is a screen diagram illustrates an exemplary UI for the secureand lightweight tunnel configuration;

FIG. 15 is a flow diagram illustrates a policy configuration sequencesystem and method;

FIG. 16 is a flow diagram illustrates a user registration andnotification system and method, with the secure and lightweight tunnelconfiguration;

FIG. 17 is a flowchart illustrates a traffic rerouting method for thesecure and lightweight tunnel configuration;

FIG. 18 is a flowchart illustrates a tunnel interface approach for thetraffic redirection in the traffic rerouting method;

FIG. 19 is a flowchart illustrates a local policy method, with thesecure and lightweight tunnel configuration;

FIG. 20 is a mobile screen shot of a locally triggered end usernotification;

FIG. 21 is a mobile screen shot of a remotely triggered end usernotification; and

FIG. 22 is a mobile screen shot of a locally generated DNS blocknotification.

DETAILED DESCRIPTION OF THE DISCLOSURE

In various exemplary embodiments, secure and lightweight trafficforwarding systems and methods are described to cloud based networksecurity systems. The traffic forwarding systems and methods providelightweight and secure traffic forwarding tunnels to cloud based networksecurity systems (for Web and DNS). Traffic (Web and DNS) from a device,including all or containerized apps, can be routed through this tunnel.The tunnel handles proxy authentication transparently for all warrantedapps and sends an application identifier with transactions for the cloudbased network security systems to identify the app and apply applicationspecific security policies. Further, wherever beneficial (like limitingmobile data quota per app), a tunnel app can apply policies locally andgenerate security notifications locally for those events. The tunnel isa convenient mechanism to handle mobile app data and the like that ismoving away from the HTTP protocol. The systems and methods provide asecure and a lightweight solution to forward Web and DNS traffic to acloud based security and policy enforcement system, a way for a secureweb gateway to identify application associated with a (Web and DNS)transaction correctly, transparently handles cloud custom authenticationscheme for all apps, and can apply some policies locally (like 3G quotaenforcement) to save bandwidth with locally generated notification forthose transactions.

§ 1.0 Example High Level System Architecture—Cloud-Based Security System

Referring to FIG. 1, in an exemplary embodiment, a block diagramillustrates a distributed security system 100. The system 100 may, forexample, be implemented as an overlay network in a wide area network(WAN), such as the Internet, a local area network (LAN), or the like.The system 100 includes content processing nodes (PN) 110, thatproactively detect and preclude the distribution of security threats,e.g., malware, spyware, viruses, email spam, etc., and other undesirablecontent sent from or requested by an external system. The processingnodes 110 can also log activity and enforce policies. Example externalsystems may include an enterprise 200, a computer device 220, and amobile device 230, or other network and computing systemscommunicatively coupled to the system 100. In an exemplary embodiment,each of the processing nodes 110 may include a decision system, e.g.,data inspection engines that operate on a content item, e.g., a webpage, a file, an email message, or some other data or data communicationthat is sent from or requested by one of the external systems. In anexemplary embodiment, all data destined for or received from theInternet is processed through one of the processing nodes 110. Inanother exemplary embodiment, specific data specified by each externalsystem, e.g., only email, only executable files, etc., is processthrough one of the processing node 110.

Each of the processing nodes 110 may generate a decision vector D=[d1,d2, . . . , dn] for a content item of one or more parts C=[c1, c2, . . ., cm]. Each decision vector may identify a threat classification, e.g.,clean, spyware, malware, undesirable content, innocuous, spam email,unknown, etc. For example, the output of each element of the decisionvector D may be based on the output of one or more data inspectionengines. In an exemplary embodiment, the threat classification may bereduced to a subset of categories e.g., violating, non-violating,neutral, unknown. Based on the subset classification, the processingnode 110 may allow distribution of the content item, precludedistribution of the content item, allow distribution of the content itemafter a cleaning process, or perform threat detection on the contentitem. In an exemplary embodiment, the actions taken by one of theprocessing nodes 110 may be determinative on the threat classificationof the content item and on a security policy of the external system towhich the content item is being sent from or from which the content itemis being requested by. A content item is violating if, for any partC−[c1, c2, . . . , cm] of the content item, at any of the processingnodes 110, any one of the data inspection engines generates an outputthat results in a classification of “violating.”

Each of the processing nodes 110 may be implemented by one or more ofcomputer and communication devices, e.g., server computers, gateways,switches, etc., such as the server 300 described in FIG. 3. In anexemplary embodiment, the processing nodes 110 may serve as an accesslayer 150. The access layer 150 may, for example, provide externalsystem access to the security system 100. In an exemplary embodiment,each of the processing nodes 110 may include Internet gateways and oneor more servers, and the processing nodes 110 may be distributed througha geographic region, e.g., throughout a country, region, campus, etc.According to a service agreement between a provider of the system 100and an owner of an external system, the system 100 may thus providesecurity protection to the external system at any location throughoutthe geographic region.

Data communications may be monitored by the system 100 in a variety ofways, depending on the size and data requirements of the externalsystem. For example, an enterprise 200 may have multiple routers,switches, etc. that are used to communicate over the Internet, and therouters, switches, etc. may be configured to establish communicationsthrough the nearest (in traffic communication time, for example)processing node 110. A mobile device 230 may be configured tocommunicated to a nearest processing node 110 through any availablewireless access device, such as an access point, or a cellular gateway.A single computer device 220, such as a consumer's personal computer,may have its browser and email program configured to access the nearestprocessing node 110, which, in turn, serves as a proxy for the computerdevice 220. Alternatively, an Internet provider may have all of itscustomer traffic processed through the processing nodes 110.

In an exemplary embodiment, the processing nodes 110 may communicatewith one or more authority nodes (AN) 120. The authority nodes 120 maystore policy data for each external system and may distribute the policydata to each of the processing nodes 110. The policy may, for example,define security policies for a protected system, e.g., security policiesfor the enterprise 200. Example policy data may define access privilegesfor users, web sites and/or content that is disallowed, restricteddomains, etc. The authority nodes 120 may distribute the policy data tothe access nodes 110. In an exemplary embodiment, the authority nodes120 may also distribute threat data that includes the classifications ofcontent items according to threat classifications, e.g., a list of knownviruses, a list of known malware sites, spam email domains, a list ofknown phishing sites, etc. The distribution of threat data between theprocessing nodes 110 and the authority nodes 120 may implemented by pushand pull distribution schemes described in more detail below. In anexemplary embodiment, each of the authority nodes 120 may be implementedby one or more computer and communication devices, e.g., servercomputers, gateways, switches, etc., such as the server 300 described inFIG. 3. In some exemplary embodiments, the authority nodes 120 may serveas an application layer 160. The application layer 160 may, for example,manage and provide policy data, threat data, and data inspection enginesand dictionaries for the processing nodes 110.

Other application layer functions may also be provided in theapplication layer 170, such as a user interface (UI) front-end 130. Theuser interface front-end 130 may provide a user interface through whichusers of the external systems may provide and define security policies,e.g., whether email traffic is to be monitored, whether certain websites are to be precluded, etc. Another application capability that maybe provided through the user interface front-end 130 is securityanalysis and log reporting. The underlying data on which the securityanalysis and log reporting functions operate are stored in logging nodes(LN) 140, which serve as a data logging layer 160. Each of the loggingnodes 140 may store data related to security operations and networktraffic processed by the processing nodes 110 for each external system.In an exemplary embodiment, the logging node 140 data may be anonymizedso that data identifying an enterprise is removed or obfuscated. Forexample, identifying data may be removed to provide an overall systemsummary of security processing for all enterprises and users withoutrevealing the identity of any one account. Alternatively, identifyingdata may be obfuscated, e.g., provide a random account number each timeit is accessed, so that an overall system summary of security processingfor all enterprises and users may be broken out by accounts withoutrevealing the identity of any one account. In another exemplaryembodiment, the identifying data and/or logging node 140 data may befurther encrypted, e.g., so that only the enterprise (or user if asingle user account) may have access to the logging node 140 data forits account. Other processes of anonymizing, obfuscating, or securinglogging node 140 data may also be used.

In an exemplary embodiment, an access agent 180 may be included in theexternal systems. For example, the access agent 180 is deployed in theenterprise 200. The access agent 180 may, for example, facilitatesecurity processing by providing a hash index of files on a clientdevice to one of the processing nodes 110, or may facilitateauthentication functions with one of the processing nodes 110, e.g., byassigning tokens for passwords and sending only the tokens to aprocessing node so that transmission of passwords beyond the networkedge of the enterprise is minimized. Other functions and processes mayalso be facilitated by the access agent 180. In an exemplary embodiment,the processing node 110 may act as a forward proxy that receives userrequests to external servers addressed directly to the processing node110. In another exemplary embodiment, the processing node 110 may accessuser requests that are passed through the processing node 110 in atransparent mode. A protected system, e.g., enterprise 200, may, forexample, choose one or both of these modes. For example, a browser maybe configured either manually or through the access agent 180 to accessthe processing node 110 in a forward proxy mode. In the forward proxymode, all accesses are addressed to the processing node 110.

In an exemplary embodiment, an enterprise gateway may be configured sothat user requests are routed through the processing node 110 byestablishing a communication tunnel between enterprise gateway and theprocessing node 110. For establishing the tunnel, existing protocolssuch as generic routing encapsulation (GRE), layer two tunnelingprotocol (L2TP), or other Internet Protocol (IP) security protocols maybe used. In another exemplary embodiment, the processing nodes 110 maybe deployed at Internet service provider (ISP) nodes. The ISP nodes mayredirect subject traffic to the processing nodes 110 in a transparentproxy mode. Protected systems, such as the enterprise 200, may use amultiprotocol label switching (MPLS) class of service for indicating thesubject traffic that is to be redirected. For example, at the within theenterprise the access agent 180 may be configured to perform MPLSlabeling. In another transparent proxy mode exemplary embodiment, aprotected system, such as the enterprise 200, may identify theprocessing node 110 as a next hop router for communication with theexternal servers.

Generally, the distributed security system 100 may generally refer to anexemplary cloud-based security system. Cloud computing systems andmethods abstract away physical servers, storage, networking, etc. andinstead offer these as on-demand and elastic resources. The NationalInstitute of Standards and Technology (NIST) provides a concise andspecific definition which states cloud computing is a model for enablingconvenient, on-demand network access to a shared pool of configurablecomputing resources (e.g., networks, servers, storage, applications, andservices) that can be rapidly provisioned and released with minimalmanagement effort or service provider interaction. Cloud computingdiffers from the classic client-server model by providing applicationsfrom a server that are executed and managed by a client's web browser,with no installed client version of an application required.Centralization gives cloud service providers complete control over theversions of the browser-based applications provided to clients, whichremoves the need for version upgrades or license management onindividual client computing devices. The phrase “software as a service”(SaaS) is sometimes used to describe application programs offeredthrough cloud computing. A common shorthand for a provided cloudcomputing service (or even an aggregation of all existing cloudservices) is “the cloud.” The distributed security system 100 isillustrated herein as one exemplary embodiment of a cloud-based system,and those of ordinary skill in the art will recognize the cloud basedmobile device security and policy systems and methods contemplateoperation on any cloud based system.

§ 2.0 Example Detailed System Architecture and Operation

Referring to FIG. 2, in an exemplary embodiment, a block diagramillustrates various components of the distributed security system 100 inmore detail. Although FIG. 2 illustrates only one representativecomponent processing node 110, authority node 120 and logging node 140,those of ordinary skill in the art will appreciate there may be many ofeach of the component nodes 110, 120 and 140 present in the system 100.A wide area network (WAN) 101, such as the Internet, or some othercombination of wired and/or wireless networks, communicatively couplesthe processing node 110, the authority node 120, and the logging node140 therebetween. The external systems 200, 220 and 230 likewisecommunicate over the WAN 101 with each other or other data providers andpublishers. Some or all of the data communication of each of theexternal systems 200, 220 and 230 may be processed through theprocessing node 110.

FIG. 2 also shows the enterprise 200 in more detail. The enterprise 200may, for example, include a firewall (FW) 202 protecting an internalnetwork that may include one or more enterprise servers 216, alightweight directory access protocol (LDAP) server 212, and other dataor data stores 214. Another firewall 203 may protect an enterprisesubnet that can include user computers 206 and 208 (e.g., laptop anddesktop computers). The enterprise 200 may communicate with the WAN 101through one or more network devices, such as a router, gateway, switch,etc. The LDAP server 212 may store, for example, user login credentialsfor registered users of the enterprise 200 system. Such credentials mayinclude a user identifiers, login passwords, and a login historyassociated with each user identifier. The other data stores 214 mayinclude sensitive information, such as bank records, medical records,trade secret information, or any other information warranting protectionby one or more security measures.

In an exemplary embodiment, a client access agent 180 a may be includedon a client computer 208. The client access agent 180 a may, forexample, facilitate security processing by providing a hash index offiles on the user computer 208 to a processing node 110 for malware,virus detection, etc. Other security operations may also be facilitatedby the access agent 180 a. In another exemplary embodiment, a serveraccess agent 180 may facilitate authentication functions with theprocessing node 110, e.g., by assigning tokens for passwords and sendingonly the tokens to the processing node 110 so that transmission ofpasswords beyond the network edge of the enterprise 200 is minimized.Other functions and processes may also be facilitated by the serveraccess agent 180 b. The computer device 220 and the mobile device 230may also store information warranting security measures, such aspersonal bank records, medical information, and login information, e.g.,login information to the server 206 of the enterprise 200, or to someother secured data provider server. The computer device 220 and themobile device 230 can also store information warranting securitymeasures, such as personal bank records, medical information, and logininformation, e.g., login information to a server 216 of the enterprise200, or to some other secured data provider server.

§ 2.1 Example Processing Node Architecture

In an exemplary embodiment, the processing nodes 110 are external tonetwork edges of the external systems 200, 220 and 230. Each of theprocessing nodes 110 stores security policies 113 received from theauthority node 120 and monitors content items requested by or sent fromthe external systems 200, 220 and 230. In an exemplary embodiment, eachof the processing nodes 110 may also store a detection process filter112 and/or threat data 114 to facilitate the decision of whether acontent item should be processed for threat detection. A processing nodemanager 118 may manage each content item in accordance with the securitypolicy data 113, and the detection process filter 112 and/or threat data114, if stored at the processing node 110, so that security policies fora plurality of external systems in data communication with theprocessing node 110 are implemented external to the network edges foreach of the external systems 200, 220 and 230. For example, depending onthe classification resulting from the monitoring, the content item maybe allowed, precluded, or threat detected. In general, content itemsthat are already classified as “clean” or not posing a threat can beallowed, while those classified as “violating” may be precluded. Thosecontent items having an unknown status, e.g., content items that havenot been processed by the system 100, may be threat detected to classifythe content item according to threat classifications.

The processing node 110 may include a state manager 116A. The statemanager 116A may be used to maintain the authentication and theauthorization states of users that submit requests to the processingnode 110. Maintenance of the states through the state manager 116A mayminimize the number of authentication and authorization transactionsthat are necessary to process a request. The processing node 110 mayalso include an epoch processor 116B. The epoch processor 116B may beused to analyze authentication data that originated at the authoritynode 120. The epoch processor 116B may use an epoch ID to furthervalidate the authenticity of authentication data. The processing node110 may further include a source processor 116C. The source processor116C may be used to verify the source of authorization andauthentication data. The source processor 116C may identify improperlyobtained authorization and authentication data, enhancing the securityof the network. Collectively, the state manager 116A, the epochprocessor 116B, and the source processor 116C operate as data inspectionengines.

Because the amount of data being processed by the processing nodes 110may be substantial, the detection processing filter 112 may be used asthe first stage of an information lookup procedure. For example, thedetection processing filter 112 may be used as a front end to a lookingof the threat data 114. Content items may be mapped to index values ofthe detection processing filter 112 by a hash function that operates onan information key derived from the information item. The informationkey is hashed to generate an index value (i.e., a bit position). A valueof zero in a bit position in the guard table can indicate, for example,absence of information, while a one in that bit position can indicatepresence of information. Alternatively, a one could be used to representabsence, and a zero to represent presence. Each content item may have aninformation key that is hashed. For example, the processing node manager118 may identify the Uniform Resource Locator (URL) address of URLrequests as the information key and hash the URL address; or mayidentify the file name and the file size of an executable fileinformation key and hash the file name and file size of the executablefile. Hashing an information key to generate an index and checking a bitvalue at the index in the detection processing filter 112 generallyrequires less processing time than actually searching threat data 114.The use of the detection processing filter 112 may improve the failurequery (i.e., responding to a request for absent information) performanceof database queries and/or any general information queries. Because datastructures are generally optimized to access information that is presentin the structures, failure query performance has a greater effect on thetime required to process information searches for very rarely occurringitems, e.g., the presence of file information in a virus scan log or acache where many or most of the files transferred in a network have notbeen scanned or cached. Using the detection processing filter 112,however, the worst case additional cost is only on the order of one, andthus its use for most failure queries saves on the order of m log m,where m is the number of information records present in the threat data114.

The detection processing filter 112 thus improves performance of querieswhere the answer to a request for information is usually positive. Suchinstances may include, for example, whether a given file has been virusscanned, whether content at a given URL has been scanned forinappropriate (e.g., pornographic) content, whether a given fingerprintmatches any of a set of stored documents, and whether a checksumcorresponds to any of a set of stored documents. Thus, if the detectionprocessing filter 112 indicates that the content item has not beenprocessed, then a worst case null lookup operation into the threat data114 is avoided, and a threat detection can be implemented immediately.The detection processing filter 112 thus complements the threat data 114that capture positive information. In an exemplary embodiment, thedetection processing filter 112 may be a Bloom filter implemented by asingle hash function. The Bloom filter may be sparse table, i.e., thetables include many zeros and few ones, and the hash function is chosento minimize or eliminate false negatives which are, for example,instances where an information key is hashed to a bit position and thatbit position indicates that the requested information is absent when itis actually present.

§ 2.2 Example Authority Node Architecture

In general, the authority node 120 includes a data store that storesmaster security policy data 123 for each of the external systems 200,220 and 230. An authority node manager 128 may be used to manage themaster security policy data 123, e.g., receive input from users of eachof the external systems defining different security policies, and maydistribute the master security policy data 123 to each of the processingnodes 110. The processing nodes 110 then store a local copy of thesecurity policy data 113. The authority node 120 may also store a masterdetection process filter 122. The detection processing filter 122 mayinclude data indicating whether content items have been processed by oneor more of the data inspection engines 116 in any of the processingnodes 110. The authority node manager 128 may be used to manage themaster detection processing filter 122, e.g., receive updates from aprocessing nodes 110 when the processing node 110 has processed acontent item and update the master detection processing filter 122. Forexample, the master detection processing filter 122 may be distributedto the processing nodes 110, which then store a local copy of thedetection processing filter 112.

In an exemplary embodiment, the authority node 120 may include an epochmanager 126. The epoch manager 126 may be used to generateauthentication data associated with an epoch ID. The epoch ID of theauthentication data is a verifiable attribute of the authentication datathat can be used to identify fraudulently created authentication data.In an exemplary embodiment, the detection processing filter 122 may be aguard table. The processing node 110 may, for example, use theinformation in the local detection processing filter 112 to quicklydetermine the presence and/or absence of information, e.g., whether aparticular URL has been checked for malware; whether a particularexecutable has been virus scanned, etc. The authority node 120 may alsostore master threat data 124. The master threat data 124 may classifycontent items by threat classifications, e.g., a list of known viruses,a list of known malware sites, spam email domains, list of known ordetected phishing sites, etc. The authority node manager 128 may be usedto manage the master threat data 124, e.g., receive updates from theprocessing nodes 110 when one of the processing nodes 110 has processeda content item and update the master threat data 124 with any pertinentresults. In some implementations, the master threat data 124 may bedistributed to the processing nodes 110, which then store a local copyof the threat data 114. In another exemplary embodiment, the authoritynode 120 may also monitor the health of each of the processing nodes110, e.g., the resource availability in each of the processing nodes110, detection of link failures, etc. Based on the observed health ofeach of the processing nodes 110, the authority node 120 may redirecttraffic among the processing nodes 110 and/or balance traffic among theprocessing nodes 110. Other remedial actions and processes may also befacilitated by the authority node 110.

§ 2.3 Example Processing Node and Authority Node Communications

The processing node 110 and the authority node 120 may be configuredaccording to one or more push and pull processes to manage content itemsaccording to security policy data 113 and/or 123, detection processfilters 112 and/or 122, and the threat data 114 and/or 124. In a threatdata push implementation, each of the processing nodes 110 stores policydata 113 and threat data 114. The processing node manager 118 determineswhether a content item requested by or transmitted from an externalsystem is classified by the threat data 114. If the content item isdetermined to be classified by the threat data 114, then the processingnode manager 118 may manage the content item according to the securityclassification of the content item and the security policy of theexternal system. If, however, the content item is determined to not beclassified by the threat data 114, then the processing node manager 118may cause one or more of the data inspection engines 117 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120.

The authority node manager 128, in response to receiving the threat dataupdate, updates the master threat data 124 stored in the authority nodedata store according to the threat data update received from theprocessing node 110. In an exemplary embodiment, the authority nodemanager 128 may automatically transmit the updated threat data to theother processing nodes 110. Accordingly, threat data for new threats asthe new threats are encountered are automatically distributed to eachprocessing node 110. Upon receiving the new threat data from theauthority node 120, each of processing node managers 118 may store theupdated threat data in the locally stored threat data 114.

In a threat data pull and push implementation, each of the processingnodes 110 stores policy data 113 and threat data 114. The processingnode manager 118 determines whether a content item requested by ortransmitted from an external system is classified by the threat data114. If the content item is determined to be classified by the threatdata 114, then the processing node manager 118 may manage the contentitem according to the security classification of the content item andthe security policy of the external system. If, however, the contentitem is determined to not be classified by the threat data, then theprocessing node manager 118 may request responsive threat data for thecontent item from the authority node 120. Because processing a contentitem may consume valuable resource and time, in some implementations theprocessing node 110 may first check with the authority node 120 forthreat data 114 before committing such processing resources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data store. If responsivethreat data is stored in the master threat data 124, then the authoritynode manager 128 provide a reply that includes the responsive threatdata to the processing node 110 so that the processing node manager 118may manage the content item in accordance with the security policy data112 and the classification of the content item. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118can cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120. The authority node manager 128 can then update themaster threat data 124. Thereafter, any future requests related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

In a detection process filter and threat data push implementation, eachof the processing nodes 110 stores a detection process filter 112,policy data 113, and threat data 114. The processing node manager 118accesses the detection process filter 112 to determine whether thecontent item has been processed. If the processing node manager 118determines that the content item has been processed, it may determine ifthe content item is classified by the threat data 114. Because thedetection process filter 112 has the potential for a false positive, alookup in the threat data 114 may be implemented to ensure that a falsepositive has not occurred. The initial check of the detection processfilter 112, however, may eliminate many null queries to the threat data114, which, in turn, conserves system resources and increasesefficiency. If the content item is classified by the threat data 114,then the processing node manager 118 may manage the content item inaccordance with the security policy data 113 and the classification ofthe content item. Conversely, if the processing node manager 118determines that the content item is not classified by the threat data114, or if the processing node manager 118 initially determines throughthe detection process filter 112 that the content item is not classifiedby the threat data 114, then the processing node manager 118 may causeone or more of the data inspection engines 116 to perform the threatdetection processes to classify the content item according to a threatclassification. Once the content item is classified, the processing nodemanager 118 generates a threat data update that includes data indicatingthe threat classification for the content item from the threat detectionprocess, and transmits the threat data update to one of the authoritynodes 120.

The authority node manager 128, in turn, may update the master threatdata 124 and the master detection process filter 122 stored in theauthority node data store according to the threat data update receivedfrom the processing node 110. In an exemplary embodiment, the authoritynode manager 128 may automatically transmit the updated threat data anddetection processing filter to other processing nodes 110. Accordingly,threat data and the detection processing filter for new threats as thenew threats are encountered are automatically distributed to eachprocessing node 110, and each processing node 110 may update its localcopy of the detection processing filter 112 and threat data 114.

In a detection process filter and threat data pull and pushimplementation, each of the processing nodes 110 stores a detectionprocess filter 112, policy data 113, and threat data 114. The processingnode manager 118 accesses the detection process filter 112 to determinewhether the content item has been processed. If the processing nodemanager 118 determines that the content item has been processed, it maydetermine if the content item is classified by the threat data 114.Because the detection process filter 112 has the potential for a falsepositive, a lookup in the threat data 114 can be implemented to ensurethat a false positive has not occurred. The initial check of thedetection process filter 112, however, may eliminate many null queriesto the threat data 114, which, in turn, conserves system resources andincreases efficiency. If the processing node manager 118 determines thatthe content item has not been processed, it may request responsivethreat data for the content item from the authority node 120. Becauseprocessing a content item may consume valuable resource and time, insome implementations the processing node 110 may first check with theauthority node 120 for threat data 114 before committing such processingresources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data 120 store. Ifresponsive threat data is stored in the master threat data 124, then theauthority node manager 128 provides a reply that includes the responsivethreat data to the processing node 110 so that the processing nodemanager 118 can manage the content item in accordance with the securitypolicy data 112 and the classification of the content item, and furtherupdate the local detection processing filter 112. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118may cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120. The authority node manager 128 may then update themaster threat data 124. Thereafter, any future requests for related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

The various push and pull data exchange processes provided above areexemplary processes for which the threat data and/or detection processfilters may be updated in the system 100 of FIGS. 1 and 2. Other updateprocesses, however, are contemplated with the present invention. Thedata inspection engines 116, processing node manager 118, authority nodemanager 128, user interface manager 132, logging node manager 148, andauthority agent 180 may be realized by instructions that upon executioncause one or more processing devices to carry out the processes andfunctions described above. Such instructions can, for example, includeinterpreted instructions, such as script instructions, e.g., JavaScriptor ECMAScript instructions, or executable code, or other instructionsstored in a non-transitory computer readable medium. Other processingarchitectures can also be used, e.g., a combination of speciallydesigned hardware and software, for example.

§ 3.0 Exemplary Server Architecture

Referring to FIG. 3, in an exemplary embodiment, a block diagramillustrates a server 300 which may be used in the system 100, in othersystems, or standalone. Any of the processing nodes 110, the authoritynodes 120, and the logging nodes 140 may be formed through one or moreservers 300. Further, the computer device 220, the mobile device 230,the servers 208, 216, etc. may include the server 300 or a similarstructure. The server 300 may be a digital computer that, in terms ofhardware architecture, generally includes a processor 302, input/output(I/O) interfaces 304, a network interface 306, a data store 308, andmemory 310. It should be appreciated by those of ordinary skill in theart that FIG. 3 depicts the server 300 in an oversimplified manner, anda practical embodiment may include additional components and suitablyconfigured processing logic to support known or conventional operatingfeatures that are not described in detail herein. The components (302,304, 306, 308, and 310) are communicatively coupled via a localinterface 312. The local interface 312 may be, for example but notlimited to, one or more buses or other wired or wireless connections, asis known in the art. The local interface 312 may have additionalelements, which are omitted for simplicity, such as controllers, buffers(caches), drivers, repeaters, and receivers, among many others, toenable communications. Further, the local interface 312 may includeaddress, control, and/or data connections to enable appropriatecommunications among the aforementioned components.

The processor 302 is a hardware device for executing softwareinstructions. The processor 302 may be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the server 300, asemiconductor-based microprocessor (in the form of a microchip or chipset), or generally any device for executing software instructions. Whenthe server 300 is in operation, the processor 302 is configured toexecute software stored within the memory 310, to communicate data toand from the memory 310, and to generally control operations of theserver 300 pursuant to the software instructions. The I/O interfaces 304may be used to receive user input from and/or for providing systemoutput to one or more devices or components. User input may be providedvia, for example, a keyboard, touch pad, and/or a mouse. System outputmay be provided via a display device and a printer (not shown). I/Ointerfaces 304 may include, for example, a serial port, a parallel port,a small computer system interface (SCSI), a serial ATA (SATA), a fibrechannel, Infiniband, iSCSI, a PCI Express interface (PCI-x), an infrared(IR) interface, a radio frequency (RF) interface, and/or a universalserial bus (USB) interface.

The network interface 306 may be used to enable the server 300 tocommunicate on a network, such as the Internet, the WAN 101, theenterprise 200, and the like, etc. The network interface 306 mayinclude, for example, an Ethernet card or adapter (e.g., 10BaseT, FastEthernet, Gigabit Ethernet, 10 GbE) or a wireless local area network(WLAN) card or adapter (e.g., 802.11a/b/g/n). The network interface 306may include address, control, and/or data connections to enableappropriate communications on the network. A data store 308 may be usedto store data. The data store 308 may include any of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,and the like)), nonvolatile memory elements (e.g., ROM, hard drive,tape, CDROM, and the like), and combinations thereof. Moreover, the datastore 308 may incorporate electronic, magnetic, optical, and/or othertypes of storage media. In one example, the data store 1208 may belocated internal to the server 300 such as, for example, an internalhard drive connected to the local interface 312 in the server 300.Additionally in another embodiment, the data store 308 may be locatedexternal to the server 300 such as, for example, an external hard driveconnected to the I/O interfaces 304 (e.g., SCSI or USB connection). In afurther embodiment, the data store 308 may be connected to the server300 through a network, such as, for example, a network attached fileserver.

The memory 310 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, tape, CDROM, etc.), andcombinations thereof. Moreover, the memory 310 may incorporateelectronic, magnetic, optical, and/or other types of storage media. Notethat the memory 310 may have a distributed architecture, where variouscomponents are situated remotely from one another, but can be accessedby the processor 302. The software in memory 310 may include one or moresoftware programs, each of which includes an ordered listing ofexecutable instructions for implementing logical functions. The softwarein the memory 310 includes a suitable operating system (O/S) 314 and oneor more programs 316. The operating system 314 essentially controls theexecution of other computer programs, such as the one or more programs316, and provides scheduling, input-output control, file and datamanagement, memory management, and communication control and relatedservices. The one or more programs 316 may be configured to implementthe various processes, algorithms, methods, techniques, etc. describedherein.

§ 4.0 Exemplary Mobile Device Architecture

Referring to FIG. 4, in an exemplary embodiment, a block diagramillustrates a mobile device 400, which may be used in the system 100 orthe like. The mobile device 400 can be a digital device that, in termsof hardware architecture, generally includes a processor 402,input/output (I/O) interfaces 404, a radio 406, a data store 408, andmemory 410. It should be appreciated by those of ordinary skill in theart that FIG. 4 depicts the mobile device 410 in an oversimplifiedmanner, and a practical embodiment may include additional components andsuitably configured processing logic to support known or conventionaloperating features that are not described in detail herein. Thecomponents (402, 404, 406, 408, and 402) are communicatively coupled viaa local interface 412. The local interface 412 can be, for example butnot limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The local interface 412 can haveadditional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, amongmany others, to enable communications. Further, the local interface 412may include address, control, and/or data connections to enableappropriate communications among the aforementioned components.

The processor 402 is a hardware device for executing softwareinstructions. The processor 402 can be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the mobile device410, a semiconductor-based microprocessor (in the form of a microchip orchip set), or generally any device for executing software instructions.When the mobile device 410 is in operation, the processor 402 isconfigured to execute software stored within the memory 410, tocommunicate data to and from the memory 410, and to generally controloperations of the mobile device 410 pursuant to the softwareinstructions. In an exemplary embodiment, the processor 402 may includea mobile optimized processor such as optimized for power consumption andmobile applications. The I/O interfaces 404 can be used to receive userinput from and/or for providing system output. User input can beprovided via, for example, a keypad, a touch screen, a scroll ball, ascroll bar, buttons, bar code scanner, and the like. System output canbe provided via a display device such as a liquid crystal display (LCD),touch screen, and the like. The I/O interfaces 404 can also include, forexample, a serial port, a parallel port, a small computer systeminterface (SCSI), an infrared (IR) interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, and the like. The I/Ointerfaces 404 can include a graphical user interface (GUI) that enablesa user to interact with the mobile device 410. Additionally, the I/Ointerfaces 404 may further include an imaging device, i.e. camera, videocamera, etc.

The radio 406 enables wireless communication to an external accessdevice or network. Any number of suitable wireless data communicationprotocols, techniques, or methodologies can be supported by the radio406, including, without limitation: RF; IrDA (infrared); Bluetooth;ZigBee (and other variants of the IEEE 802.15 protocol); IEEE 802.11(any variation); IEEE 802.16 (WiMAX or any other variation); DirectSequence Spread Spectrum; Frequency Hopping Spread Spectrum; Long TermEvolution (LTE); cellular/wireless/cordless telecommunication protocols(e.g. 3G/4G, etc.); wireless home network communication protocols;paging network protocols; magnetic induction; satellite datacommunication protocols; wireless hospital or health care facilitynetwork protocols such as those operating in the WMTS bands; GPRS;proprietary wireless data communication protocols such as variants ofWireless USB; and any other protocols for wireless communication. Thedata store 408 may be used to store data. The data store 408 may includeany of volatile memory elements (e.g., random access memory (RAM, suchas DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g.,ROM, hard drive, tape, CDROM, and the like), and combinations thereof.Moreover, the data store 408 may incorporate electronic, magnetic,optical, and/or other types of storage media.

The memory 410 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, etc.), and combinations thereof.Moreover, the memory 410 may incorporate electronic, magnetic, optical,and/or other types of storage media. Note that the memory 410 may have adistributed architecture, where various components are situated remotelyfrom one another, but can be accessed by the processor 402. The softwarein memory 410 can include one or more software programs, each of whichincludes an ordered listing of executable instructions for implementinglogical functions. In the example of FIG. 4, the software in the memory410 includes a suitable operating system (O/S) 414 and programs 416. Theoperating system 414 essentially controls the execution of othercomputer programs, and provides scheduling, input-output control, fileand data management, memory management, and communication control andrelated services. The programs 416 may include various applications,add-ons, etc. configured to provide end user functionality with themobile device 400. For example, exemplary programs 416 may include, butnot limited to, a web browser, social networking applications, streamingmedia applications, games, mapping and location applications, electronicmail applications, financial applications, and the like. In a typicalexample, the end user typically uses one or more of the programs 416along with a network such as the system 100.

§ 5.0 Exemplary General Cloud System

Referring to FIG. 5A, in an exemplary embodiment, a cloud system 500 isillustrated for implementing the systems and methods described herein.The cloud system 500 includes one or more cloud nodes (CN) 502communicatively coupled to the Internet 504. The cloud nodes 502 mayinclude the processing nodes 110, the server 300, or the like. That is,the cloud system 500 may include the distributed security system 100 oranother implementation of a cloud based system. In the cloud system 500,traffic from various locations (and various devices located therein)such as a regional office 510, headquarters 520, various employee'shomes 530, mobile laptop 540, and mobile device 542 is redirected to thecloud through the cloud nodes 502. That is, each of the locations 510,520, 530, 540, 542 is communicatively coupled to the Internet 504through the cloud nodes 502. The cloud system 500 may be configured toperform various functions such as spam filtering, uniform resourcelocator (URL) filtering, antivirus protection, bandwidth control, dataloss prevention, zero day vulnerability protection, web 2.0 features,and the like. In an exemplary embodiment, the cloud system 500 and thedistributed security system 100 may be viewed as Security-as-a-Servicethrough the cloud.

In an exemplary embodiment, the cloud system 500 can be configured toprovide mobile device security and policy systems and methods. Themobile device 542 may be the mobile device 400, and may include commondevices such as smartphones, tablets, netbooks, personal digitalassistants, MP3 players, cell phones, e-book readers, and the like. Thecloud system 500 is configured to provide security and policyenforcement for devices including the mobile devices 542 in the cloud.Advantageously, the cloud system 500 avoids platform specific securityapps on the mobile devices 542, forwards web traffic through the cloudsystem 500, enables network administrators to define policies in thecloud, and enforces/cleans traffic in the cloud prior to delivery to themobile devices 542. Further, through the cloud system 500, networkadministrators may define user centric policies tied to users, notdevices, with the policies being applied regardless of the device usedby the user. The cloud system 500 provides 24×7 security with no needfor updates as the cloud system 500 is always up-to-date with currentthreats and without requiring device signature updates. Also, the cloudsystem 500 enables multiple enforcement points, centralized provisioningand logging, automatic traffic routing to a nearest cloud node 502,geographical distribution of the cloud nodes 502, policy shadowing ofusers which is dynamically available at the cloud nodes, etc.

§ 5.1 DNS Augmented Security

In various exemplary embodiments, the cloud system 500 and/or thedistributed security system 100 can be used to perform DNS surrogation.Specifically, DNS surrogation can be a framework for distributed orcloud-based security/monitoring as is described herein. Endpointsecurity is no longer effective as deployments move to the cloud withusers accessing content from a plurality of devices in an anytime,anywhere connected manner. As such, cloud-based security is the mosteffective means to ensure network protection where different devices areused to access network resources. Traffic inspection in the distributedsecurity system 100 and the cloud-based system 500 is performed in anin-line manner, i.e. the processing nodes 110 and the cloud nodes 500are in the data path of connecting users. Another approach can include apassive approach to the data path. DNS is one of the most fundamental IPprotocols. With DNS surrogation as a technique, it is proposed to useDNS for dynamic routing of traffic, per user authentication and policyenforcement, and the like.

In conjunction with the cloud system 500 and/or the distributed securitysystem 100, various techniques can be used for monitoring which aredescribed on a sliding scale between always inline to never inline.First, in an always inline manner, all user traffic is between inlineproxies such as the processing nodes 110 or the cloud nodes 502 withoutexception. Here, DNS can be used as a forwarding mechanism to the inlineproxies. Second, in a somewhat always inline manner, all user trafficexcept for certain business partners or third parties is between inlineproxies such as the processing nodes 110 or the cloud nodes 502. Third,in an inline manner for most traffic, high bandwidth applications can beconfigured to bypass the inline proxies such as the processing nodes 110or the cloud nodes 502. Exemplary high bandwidth applications caninclude content streaming such as video (e.g., Netflix, Hulu, YouTube,etc.) or audio (e.g., Pandora, etc.). Fourth, in a mixed manner, inlinemonitoring can be used for “interesting” traffic as determined bysecurity policy with other traffic being direct. Fifth, in an almostnever inline manner, simple domain-level URL filtering can be used todetermine what is monitored inline. Finally, sixth, in a never inlinemanner, DNS augmented security can be used.

Referring to FIG. 5B, in an exemplary embodiment, a network diagramillustrates a network 550 with a distributed security cloud 552providing DNS augmented security. The network 550 includes a user device554 connecting to the distributed security cloud 552 via an anycast DNSserver 556. The anycast DNS server 556 can be a server such as theserver 300 of FIG. 3. Also, the anycast DNS server 556 can be theprocessing node 110, the cloud node 502, etc. The distributed securitycloud 552 includes the anycast DNS server 556, policy data 558, and aninline proxy 560. The inline proxy 560 can include the processing node110, the cloud node 502, etc. In operation, the user device 554 isconfigured with a DNS entry of the anycast DNS server 556, and theanycast DNS server 556 can perform DNS surrogation as is describedherein. The distributed security cloud 552 utilizes the anycast DNSserver 556, the policy data 558, and the inline proxy 560 to perform theDNS augmented security.

The network 550 illustrates the DNS augmented security where DNSinformation is used as follows. First, at a step 562, the user device554 requests a DNS lookup of a site, e.g. “what is the IP address ofsite.com?” from the anycast DNS server 556. The anycast DNS server 556accesses the policy data 558 to determine the policy associated with thesite at step 564. The anycast DNS server 556 returns the IP address ofthe site based on the appropriate policy at step 566. The policy data558 determines if the site either goes direct (step 568) to theInternet, is inspected by the inline proxy (step 570), or is blocked perpolicy (step 572). Here, the anycast DNS server 556 returns the IPaddress with additional information if the site is inspected or blocked.For example, if the anycast DNS server 556 determines the access isdirect, the anycast DNS server 556 simply returns the IP address of thesite. If the anycast DNS server 556 determines the site is blocked orinspected, the anycast DNS server 556 returns the IP address to theinline proxy 560 with additional information. The inline proxy 560 canblock the site or provide fully inline proxied traffic to the site (step574) after performing monitoring for security.

The DNS augmented security advantageously is protocol and applicationagnostic providing visibility and control across virtually allInternet-bound traffic. For example, DNS-based protocols includeInternet Relay Chat (IRC), Session Initiation Protocol (SIP), HypertextTransfer Protocol (HTTP), HTTP Secure (HTTPS), Post Office Protocol v3(POP3), Internet Message Access Protocol (IMAP), etc. Further, emergingthreats are utilizing DNS today especially Botnets and advancedpersistent threats (APTs). For example, Fast flux is a DNS techniqueused to hide phishing and malware delivery sites behind an ever-changingnetwork of compromised hosts acting as proxies. The DNS augmentedsecurity provides deployment flexibility when full inline monitoring isnot feasible. For example, this can be utilized in highly distributedwith high bandwidth environments, in locations with challenging InternetAccess, etc. The DNS augmented security can provide URL filtering,white/black list enforcement, etc. for enhanced security without contentfiltering. In this manner, the network 550 can be used with thedistributed security system 100 and the cloud system 500 to providecloud-based security without requiring full inline connectivity.

§ 6.0 Web Transaction Archiving System

Referring to FIG. 6, in an exemplary embodiment, a functional blockdiagram illustrates a web transaction archiving system 600. Thearchiving system 600 can be based on the systems 100, 500, or anothertype of system. That is, the archiving system 600 can operate on anycloud system handling web or any other data transactions. The archivingsystem 600 includes a cloud processing node 610, a cloud management node620, a cloud Simple Mail Transfer Protocol (SMTP) node 630, a cloudlogging node 640, and a customer SMTP server 650. In an exemplaryembodiment, the cloud processing node 610 can be the processing node 110or the cloud node 502, the cloud management node 620 can be theauthority node 120 or part of the cloud node 502, and the logging node640 can be the logging node 140 or part of the cloud node 502. The cloudSMTP node 630 can be part of any of the logging node 140, the processingnode 110, the authority node 120, the cloud node 502, or a standalonedevice. Collectively, the nodes 610, 620, 630, 640 are part of a cloudsystem, i.e. the system 100, 500, etc. The customer SMTP server 650 is amail server located within an organization's administrative domain. Forexample, in FIG. 2, the customer SMTP server 650 could be within theenterprise 200 behind the firewalls 202, 203.

In operation, the cloud processing node 610 interfaces to end users 660,such as receiving HTTP requests or any other data (e.g., collectivelyreferred to as web transactions or app transactions). The cloudprocessing node 610 is configured to perform the various functionsdescribed herein for the processing node 110 and the cloud node 502.That is, the cloud processing node 610 can perform data analysis on anyrequests to/from the end users. In context of this data analysis, thearchiving systems and methods seek to avoid storing any private dataassociated with the organization within the confines of the cloud. Thecloud processing node 610 performs the data analysis based on policyinformation provided by the cloud management node 620 (i.e., previouslyprovided, provided on-demand, etc.). Part of this policy information caninclude archiving rule for specific security policies. Exemplaryarchiving rules can include, without limitation, not storing datarelated to a security incident event (e.g., a data leakage event, etc.),not storing data related to accessing certain Web sites, not storingdata related to specific users, etc. Through the cloud management node620, the archiving rules can be modified as needed by an ITrepresentative of an organization. The cloud logging node 640 is usedfor storing notification logs related to the data analysis. In anexemplary embodiment, the cloud logging node 640 can store a log entryfor any event detected at the cloud processing node 610. However, thedata in the log entry can be based on the archiving rules. For example,a security incident event could just denote the specifics of the eventwithout storing the associated data at the cloud logging node 640.

The cloud SMTP node 630 is configured to handle archiving of data whenthere is an archiving rule in place. The cloud SMTP node 630 isconfigured to receive a notification when there is an event and anarchiving rule in place. For example, assuming the cloud SMTP node 630is separated from the cloud processing node 610, the cloud SMTP node 630can receive an email notification from the cloud processing node 610.Alternatively, the cloud SMTP node 630 can be part of the cloudprocessing node 610, i.e. part of the processing node 110, the cloudnode 502, etc., and in this exemplary embodiment, the cloud processingnode 610 can simply internally notify the cloud SMTP node 630. The cloudSMTP node 630 is configured to compose an email to the customer SMTPserver 650 based on the archiving rule and to securely transmit theemail to the customer SMTP server 650. Subsequent to the emailtransmission, the cloud, i.e. the nodes 610, 620, 630, 640, no longerhas the data related to the event. The data is securely within theorganization's domain in the customer SMTP server 650. The customer SMTPserver 650 can include functionality to automatically archive the datain the email in a customer managed log. Thus, the archiving systems andmethods provide dual benefits i.e. limiting data storage in the cloudwhile honoring data privacy requirements of the customer.

§ 7.0 Web Transaction Archiving Methods

Referring to FIG. 7, in an exemplary embodiment, a flow diagramillustrates an archiving method 700. The archiving method 700 can beimplemented with the web transaction archiving system 600, the cloudsystem 500, the distributed security system 100, etc. The archivingmethod 700 is illustrated relative to functions associated with thenodes 610, 630, 640, 650, the end user 660, and a recipient 670 atcompany X with company X being the organization associated with the enduser 660 (i.e., the data belongs to company X). To start, a webtransaction (or any data transaction) with a violation is presented tothe archiving method 700. Specifically, the archiving method 700processes outputs from a security processing engine, e.g. such asdescribed herein in the functionality of the processing node 110 and thecloud node 502. The archiving method 700 is presented with contentextract which triggers the security event or violation, originalcontent, security policy, etc. The archiving method 700 can beimplemented based on a setting or policy of archiving content associatedwith violations. The cloud processing node 610 detects a web transactionwith a violation (step 702). Note, this violation is one in whicharchiving rules require the data to be stored with company X's domainand not in the cloud. The cloud processing node 610 provides a messageto customer SMTP server 650 (step 704).

In an exemplary embodiment, the message is an email notification withTransport Layer Security (TLS) and data including a Web User ID of theuser associated with the violation and various data about the violation.Exemplary data about the violation can include the original Web contenttriggering the violation, Data Leakage Prevention (DLP) violationrelated data, DLP engines and dictionaries hit, etc. Specifically, theemail notification can include meta information of the web transaction,such as, URL; user of the web transaction and, in case USER is notpresent, a location; type of web transaction such as Social Networking,Web mail, Web post; names of security engine hit; and the like. Theemail notification can also include the extracted patterns whichcontribute towards the triggering of a security policy, i.e. therationale for flagging the transaction as a violation. Thus, originalcontent from Web transaction is attached to the email, and if thecontent was in file being uploaded then that file is attached to theemail. In an exemplary embodiment, the processing node 610 provides themessage to customer SMTP server 650 as described above. In anotherexemplary embodiment, the processing node 610 provides the message tothe cloud SMTP server 630 which in turn can provide the message to thecustomer SMTP server 650. Alternatively, the cloud SMTP server 630 canbe integrated with the processing node 610.

The customer SMTP server 650 (or the cloud SMTP server 630) can beconfigured to perform numerous steps. First, the SMTP server 650 cansend a notification (e.g., email, text message, URL, etc.) with theoriginal web content and security violation to a recipient 670 atcompany X (step 706). For example, the recipient 670 could be someone inIT or some other person responsible for data security and control. Thepurpose of this notification can be to alert the company X of theviolation for any reactive measures to be taken. Next, cloud SMTP server630 sends a notification to the cloud logging node 640 (step 708). Thisnotification can also be an email message with relevant data that isstored in the cloud, i.e. the relevant data does not include the datastored with company X per the archiving rule. The relevant data is dataused by the cloud system for proactive security, i.e. data related tothe violation that can be used for subsequent detections of violations.This data may be anonymized as well as excluding the data stored withcompany X per the archiving rule. The SMTP server 650 can also send anotification to a company X log 680 (step 710). The company X log 680can reside on the cloud SMTP server 630 or a separate device, and thecompany X log 680 includes a database of violations. Subsequently,company X, through this database, company X IT can search forviolations, view and prepare reports of violations, etc. providing anintegrated view for proactive security measures.

Referring to FIG. 8, in an exemplary embodiment, a flowchart illustratesan archiving method 800. The archiving method 800 can be implementedwith the web transaction archiving system 600, the cloud system 500, thedistributed security system 100, etc. In general, the method 800 can beimplemented by a computer, such as the server 300 described herein,through instructions on a computer-readable medium that are executed bythe processor 302 to cause the server 300 perform the method 800. First,the method 800 has a security incident triggered (step 802). Exemplarysecurity incidents can include malware, spyware, viruses, Trojans,botnets, email spam, policy violations, data leakage, etc. The incidentinformation is sent to a policy module (step 804). Here, an analysis isperformed on the incident including checking if there is an archivingrule match (step 806). Archiving rules can be defined per organizationper violation type, and can generally define what information is storedin the cloud and what information is securely stored with theorganization's domain, i.e. not within the cloud. If there is noarchiving rule in place (step 806), the method 800 is complete (step808). If there is an archiving rule in place (step 806), the method 800evaluates associated rules and actions based on the incident, and setsactions based thereon (step 810).

The method 800 checks if there is a notification rule (step 812). Forexample, the method 800 can include two aspects, 1) is there a rulepreventing archiving in the cloud, and 2) is there a rule requiringarchiving within an organization's domain. These two aspects can bemutually applied. For example, if there is no notification rule (step812), the method 800 can end (step 808) with the cloud system simply notstoring the data related to the incident. If there is a notificationrule (step 812), the method 800 can send the incident information andcontent to a notification module (step 814). The notification moduleconstructs a message with violation information, web content, webtransaction ID, auditor contact info, user, info, TLS, etc. and sendsthe message to an SMTP cluster (step 816). The SMTP cluster can be thecloud SMTP node 630, and generally includes equipment within the cloudto create notifications to the organization. The cloud can record theoriginal transaction with the web transaction ID (step 818). Here, thecloud, e.g. the processing node 610, the cloud SMTP node 630, etc., canlog and store information related information while adhering to therules (e.g., storing incident information without underlying content).The SMTP cluster can send the received message to a notificationApplication Programming Interface (API) (step 820). The notificationmodule constructs an email based on the received message and sends outthe email (step 822). The notification module, in the cloud, records anew transaction based on a message ID (step 824). This transaction, inthe cloud, can be recorded using a violation company ID and violationuser ID, etc. Further, the transaction can be send out for notificationto the company, users, etc. The policy module and the notificationmodule can include physical devices, hardware, software, firmware, etc.to perform the various functions in the method 800.

Referring to FIG. 9, in an exemplary embodiment, a network diagramillustrates a network 900 depicting an exemplary operation of thearchiving methods 700, 800. The network 900 includes an organization'sdomain 902, a cloud system 904, and an external network 906 (e.g., theInternet). As described herein, the cloud system 904 is an intermediatelayer between the domain 902 and the network 906, and the cloud system904 is configured to implement the archiving systems and methodsdescribed herein in conjunction with the domain 902. The domain 902includes users 660, the SMTP server 650, and, optionally, the company Xlog 680. The cloud system 604 includes the cloud processing node 610,the cloud SMTP node 630, and the cloud logging node 640. The externalnetwork 906 can include a site 910. In operation, a user 660 can accessthe site 910 through the cloud system 904, specifically through thecloud processing node 610. If there is no violation, the cloudprocessing node 610 simply acts as a proxy between the site 910 and theuser 660. If there is a violation and an associated archiving rule, thecloud processing node 610 is configured to implement the methods 700,800 with the devices 630, 640, 650, 680 to ensure no private data (perthe archiving rule) belonging the organization is stored in the cloudsystem 904, but rather stored within the domain 902 through the devices650, 680. In another exemplary embodiment, private data belonging to theorganization could be stored in the cloud system 904, but with anapproach that ensures this private data is only reviewable or accessibleby the organization. For example, the devices 610, 630, 640 couldinclude encrypted storage for storing violation information. Thisencrypted storage could a use key per organization and encrypt the datausing that key before storing the data. Thus while private data isstored in the cloud system 904, it is only accessible with theorganization's private key.

In an exemplary embodiment, a cloud based security method includesmonitoring data traffic between a user and an external network, whereinmonitoring is performed by a processing node including a first server ina cloud based system; detecting a security incident; if an archivingrule exists based on the security incident, providing a notification toa second server within an organization's domain, wherein the user ispart of the organization, and wherein the notification includes privatedata associated with the security incident based on the archiving rule;and storing non-private data in the cloud based system based on thearchiving rule. In another exemplary embodiment, a cloud based securitysystem includes a plurality of servers forming a cloud system; aprocessing module executed on the plurality of servers to detectsecurity incidents in data communications between users and an externalnetwork; a policy module executed on the plurality of servers todetermine archiving rules associated with detected security incidents;and a notification module executed on the plurality of servers toprovide notification of private data associated with the detectedsecurity incidents based on the archiving rules for storage within anassociated organization's domain. In yet another exemplary embodiment, aprocessing node in a cloud based system includes a network interfacecommunicatively coupled to a user and an external network; a processor;and memory storing computer executable instructions, and in response toexecution by the processor, the computer executable instructions causethe processing node to perform steps of: monitoring data traffic betweenthe user and the external network; detecting a security incident; if anarchiving rule exists based on the security incident, providing anotification to a server within an organization's domain, wherein theuser is part of the organization, and wherein the notification includesprivate data associated with the security incident based on thearchiving rule; and storing non-private data based on the archivingrule.

§ 8.0 Out of Band Notification System and Method

Referring to FIG. 10, in an exemplary embodiment, a flow diagramillustrates an out of band notification system 1000 and method 1001. Thenotification system 1000 includes an agent 1002, a central authority(CA) 1004, a cloud node (CN) 1006, a delegate 1008, and a mobileoperating system (OS) notification cloud 1010. Collectively, the devices1004, 1006, 1008 can be part of the distributed security system 100, thecloud system 500, the distributed security cloud 552, the cloud system904, etc. The agent 1002 is a software program or app that is installedand operated on the mobile device 400. The agent 1002 can have variousfunctionality such as authentication with the systems 100, 500, end usernotification (EUN), and the like. Additionally, the agent 1002 can bedistributed or installed through mobile OS-specific mechanisms such asGoogle Play (Android Marketplace), Apple App Store, Windows Marketplace,etc. The CA 1004 is a central authority (CA) server which can be used bythe systems 100, 500 to track users. The CN 1006 can be the processingnode 110 in the system 100 or the cloud node 502 in the system 500.

The method 1001 includes installing the agent 1002, such as an app onthe mobile device 400 (step 1011). This can be done via the mobileOS-specific mechanisms or the like. An administrator sends apreconfigured email to the mobile device 400 (step 1012) and the userexecutes a preconfigured link or the like in the email on the mobiledevice 400 (step 1013). These steps configure the agent 1002 with thespecific user and associated policy in the system 100, 500. Onceconfigured and operating, the user can perform authentication such aswith the agent 1002 through the cloud node 1006 (step 1014). Theauthentication can be anything known in the art, e.g. User ID andpassword, etc. The cloud node 1006 responds with a cookie (ifsuccessful) or error (if not successful) (step 1015). If theauthentication is successful, a device posture is sent to the CA 1004 toupdate the last User ID for the mobile device 400 (step 1016). This isto create a User ID to IP binding as is described herein such that thesystem 100, 500 can know who is using the mobile device 400.

The method 1001 can include initiating a mobile app transaction (step1017). If the mobile app transaction complies with relevant policy, doesnot contain malware, etc., the method 1001 would end here and the mobileapp transaction would be successful. If the mobile app transaction isnot successful, e.g., blocked, cautioned, etc., the CN 1006 can send anotification request URL to the delegate 1008 (step 1018). The delegate1008 sends the request to the mobile OS notification cloud 1010 (step1019), and the message can be delivered to the mobile device out of band(step 1020).

In the context of mobile security—through the systems 100, 500 and withthe mobile device 400 operating the agent 1002, there are variousdeployment and use cases. For example, there are three exemplarydeployments where mobile security can be enabled, namely:

1. Surrogate IP within enterprise (GRE without Network AddressTranslation (NAT)) (Bring your own device)

2. Global Proxy (Company Owned Device)

3. Mobile VPN

§ 8.1 Surrogate IP Within Enterprise (GRE Without NAT)

With surrogate IP, the user on the mobile device 400 has to login oncethrough a browser. With this verified credential, a gateway (e.g., theCA 1004) creates a mapping of the user to the IP. Note, the CA 1004 canbe the processing node 110 or the authority node 120. App traffic thatdoes not have ability to perform cloud authentication, now can beauthenticated using the newly built User to IP mapping. The cloud (thesystems 100, 500) can now enforce policy on App traffic as well. In thisuse case, there is a need for a clean login and logout feature thathelps setting up User to IP binding. Once the User to IP binding isestablished in the CA 1004, the system 100 can enforce policy basedthereon.

Again, when App traffic is blocked by the cloud such as based onconfigured Admin policy, the block message sent in response to theblocked request is not rendered by the apps. This is not user friendlyand there is a need to send some notification to user on the mobiledevice 400 regarding blocked transaction. The agent 1002 solves theseissued by authentication the CN 1006 creating the User to IP mapping. Asa part of the EUN feature, the agent 1002 will register with Apple,Google and Windows Push notification services, i.e. the mobile OSnotification cloud 1010.

After successful authentication app will obtain user cookie and willregister with the CA 1004—the respective tokens and related deviceinformation along with user's ID. At this point, the cloud has mappingof user to device token. Now when EUN has to be sent to a specific user,the systems 100, 500 cloud can look up the user<->device mapping andsend appropriate notifications using the mobile OS notification cloud1010, e.g. the Apple or Google push notification infrastructure.

§ 8.2 Global Proxy

With the Global proxy, each request from a mobile device will carry 407credentials for user identification. The EUN functionality is needed asexplained in previous section of surrogate IP. In this case, thefunction of authentication will be limited to getting the user cookieand registering with the CA 1004—the device mappings to user. Thesemappings will be used to send notification as explained in previoussection.

§ 8.3 Mobile VPN

With Mobile VPN, user credentials are embedded in an IPSec VPN tunnel.As with other two deployments, the EUN functionality is needed. In thiscase, the function of authentication is limited to getting the usercookie and registering the device mappings to user with the CA 1004.These mappings will be used to send EUN notification as descriptedabove.

§ 8.4 Delegate

The delegate 1008 is a group of application servers located outside ofcustomer cloud that can handle two major roles. One is to maintain CCM(customer—cloud mapping) and the other is to handle the notification toservers provided by mobile OS platform such as Apple Push NotificationService (APNS), Google Cloud Messaging (GCM) for Android, and WindowsPush Notification Service (WPNS) for the mobile OS notification cloud1010. The CCM is persisted as data within delegate 1008 domain and willbe initially populated by the delegate 1008. More importantly, thedelegate 1008 will implement the following three HTTP commands as mainapplication programming interfaces (API), namely 1) CCM lookup API, 2)Update CCM entry update API, 3) Request Notification API.

§ 8.5 Pre-Configuration of the Agent

An App specific scheme can be used to pre configure primarily. Acustomer admin can generate a welcome email to their user and the userwill execute the link in the mobile devices. The URL is designed tolaunch the secure agent 1002 app and will fill the passed informationaccordingly. The preconfigure URL can include the following information:user name and cloud info.

§ 8.6 AUL (Authorized User List)

The secure agent 1002 can be designed to work with the latest multi-userenabled mobile devices such as Nexus 10 or Surface. To do this, thesecure agent 1002 maintains an “authorized user list” called AUL asencrypted data under the app folder with the same lifetime of app. Thismeans if app is uninstalled, the user needs to be authorized again.

§ 8.7 Cloud Authentication

Authentication takes places in two steps internally although it stilllooks as one from the end user's point of view. The first step isauthorization through the gateway of cloud to acquire cookie and IPsurrogate information just like a secure browser. For example, throughthe systems 100, 500. The second step is to send cookie, device ID foreach mobile OS notification such as device token for APNS, GCM, WPNS,AUL and more collected device posture information and scanned app listto the CA 1004 for update purpose. Whoever logs in, the secure agent1002 always sends the whole AUL to the CA 1004 to ensure AUL is up todate in server side too. So the CA 1004 must differentiate its own datawith client data and update its database accordingly. A log out from appwill also clear current user from AUL.

§ 8.8 User & Device Information Database

The CA 1004 can maintain database information for each user and eachdevice. For the user, the CA 1004 can maintain information related toUser ID, login name, password, role (access list, department,organization), restrictions, updates, statistics, etc. For the device,the CA 1004 can maintain information such as device type, OS version, OStype, device model, applications, MAC address, etc. The CA 1004 can alsomaintain a list of apps installed on the device. For example,device_type codes could include:

-   00 Others-   01 iPhone/iPod touch-   02 iPad-   03 Android Mobile-   04 Android Tablet-   05 Windows Mobile-   06 Surface-   07 Blackberry-   08 Ubuntu Mobile-   09 Desktop

For example, OS type codes could include:

-   00 Others-   01 iOS-   02 Android OS-   03 Windows Mobile OS-   04 Blackberry OS-   05 Ubuntu for Phone-   06 Mac OS X-   07 Windows-   08 Linux

The CA 1004 will maintain last User ID (LUI) per device to ensure thatnotification is delivered only to the associated device. LUI will bemaintained in device info table by upon successful authentication.

§ 8.9 EUN Send and Handling

The delegate 1008 will be responsible to maintain a connection toproprietary notification servers from mobile OS such as APNS, GCM andWPNS and will handle the cloud systems 100, 500 direct or indirectnotification URL API requests. The delegate 1008 also takes suppressioninformation originated from the cloud systems 100, 500 and implement thelogic accordingly.

§ 9.0 Design and Implementation

Referring to FIG. 11, in an exemplary embodiment, a block diagramillustrates a user interface (UI) 1100 for the out of band notificationsystem 1000 of FIG. 10. The UI 1100 includes a master login U 1102 witha username that determines a login mechanism per user configuration,namely either i) a Lightweight Directory Access Protocol (LDAP) orActive Directory (AD) password login UI or ii) a Security AssertionMarkup Language (SAML) password login UI using an external IdentityProvider (IDP).

For SAML, in general, when client tries to open any page, it redirectsto a URL, e.g., gateway.zscaler.net and then user should fill usernameand if he/she is a SAML user, gateway does not ask for his password butredirects to a SAML server for authentication, then the custom SAML pagedoes the authentication per company's implementation. In the secureagent 1002, after SAML detection, the login UI will be dismissed andusername for company SAML implementation will be entered automatically,with which was entered from the previous login UI.

For the creation of device to User mapping, the CA 1004 performs thefunctions of 1) managing LLU (last login user) information after userauthentication, 2) updating device posture information of in a deviceinfo table, 3) synchronizing with the CN 1006 with additional mobilenotification related information in user configuration information, and4) updating an array of app_ids on the device. The CA 1004 has an APIwith the secure agent 1002, e.g. HTTP (443) request with POST withcontents and names and value pairs. The API can include command type andcookie information to 1) update device posture (command type=01): APIwill contain cookie and command type (=01) along with all deviceinformation of device info table except app_id array; 2) updateinstalled App Ids (command type=02), and 3) a hash messageauthentication code (HMAC) for security.

The secure agent 1002 uses the HTTP API to talk to the CA 1004. Allcalls are made over https with POST method. The full protocol isdescribed as follows. There are two end-points defined on the CA 1004,one for provisioning and registering a device and one for logging-outand de-registering a device (and its user). Provisioning end-point willbe /dev_api/add. Method POST and on registration, the CA 1004 will addthe device and return the device_id in the same request message format.Logout end-point will be /dev_api/del. Method POST and on logout, the CA1004 will dis-associate the device and the user. Further transactionsfrom this device will not be associated to this user (for logs ornotification) until user does a re-provisioning. All messages will be inthe form of multiple [type] [length] [value] triads. [2byte Type] [2byteLength][Variable length value]. A protocol version type will identifythe protocol the secure agent 1002 is talking with the CA 1004. Infuture, any major changes to the message protocol and the version numberwill could be incremented (e.g. device_type becomes string frominteger). The CA 1004 can return error on a version mismatch. Anyunknown type will be ignored and processing will move to next type (aslong as versions are same) so that secure agent 1002 changes can be doneindependently without breaking the CA 1004 protocol.

Strings can be of variable-length without the ‘\0’ character. Integerscan be of 4-byte length, multi-byte data-types can use little-endianformat, and all the command-types can be defined in a shared-header fileand generated when the CA 1004 is built and shared by the mobile code.For example, to provision a device:

[PROTOCOL_VERSION][4][0x1][COOKIE_TYPE][13][abcXXXxxxXXXD][TS_TYPE][4][0x55051451][DEV_TYPE][4][0x1][DEV_NAME][12][Joe's IPhone] etc.

The CA 1004 can perform the following actions when it receives themessage. First, the CA 1004 will parse and validate the version andtimestamp; the timestamp is expected to be in UNIX time format (so willbe an integer type) and no more than 5 minutes of skew is allowed fromcurrent-time on the CA 1004. Next, a cookie is validated and userID isextracted from the cookie. The message is parsed and the device isupdated or newly added. The notification key will be used to check if itis an device update or a new device provisioning—if notification_keyexists, the CA 1004 will update the device with any changes needed fore.g. os_type, udid, lastuserid, jailbreak, etc.; or if thenotification_key does not exist, the CA 1004 will create a new devicerecord for this userid. (It is rare for the notification key to changefor the same device).

After processing the message, the CA 1004 will either send a Success 200OK message with the device_id or a 500 Internal Error with an errorcode. The secure agent 1004 should re-try provisioning on error. Forde-provisioning, the CA 1004 will dis-associate the given userid anddeviceid. A flush is sent to the CN 1006 to forget the dis-associateddevice's notification_key.

§ 9.1 iOS Global Proxy Configuration

The secure agent 1004 provisioning message will also be used toprovision the iOS Global Proxy user & password. The device_id is theidentity of the device; primary key in the CA 1004 database; andreturned by the CA 1004 after provisioning of device. The device_loginis the login_name that will be used for iOS Global Proxy authentication.It will be of the form <device_id>@<domain>. This will be returned fromthe CA 1004 after provisioning. For example, 1000@cokecce.com [1000 isdevice ID. cokecce.com is domain of the user]. The device_password isthe auto-generated password for the device and is generated by the CA1004 and returned after provisioning.

The CA 1004 will define an end-point for changing the device_password./dev_api/chg Input will be the device_id, old device_password and thenew device_password requested. Cookie and valid timestamp are requiredin the message.

§ 9.2 UI Flow

In FIG. 11, login UI flow will be two phases. Master login UI willdetermine the authentication mechanisms. Then either password login UIjust like safe browser or SAML login UI will show. A Home UI will havecopy button both for display ID and PIN. A Notification UI is be placedthe second place in tab over report UI. It will show notification listgrouped by app. The CN 1006 will set app name as “Other App” in case appmapping to user-agent is not discovered yet. A Detail UI will displaythe detail information of the latest message among selected app group.There is a “more message” button that leads to show the previous list ofmessage. Upon selection among previous ones, detail information will berefreshed with selected previous message. There is also “email” buttonto share notification detail through email.

A Report UI, instead of showing stat from locally stored notification,it will embed UI like web UI to show stat from server. Local databasewill have only cached one which can be also deleted by user in settingUI so that it's not that useful stat. In setting UI, “Clear localnotification” button will remain as in your document.

§ 10.0 Configuration

Again, the delegate 1008 connects to the mobile OS notification cloud1010. The GCM Server will register android device and send registrationID to device. This registration ID will be forwarded by device to the CA1004. Maximum size of registration ID can be 4 KB. For example, aregistration ID will look like “APA91bHun4MxP5egoKMwt2KZFBaFUH-1RYqx.”To allow connectivity with GCM, Organization needs to open ports5228,5229 and 5230. GCM typically only uses 5228, but it sometimes uses5229 and 5230. The delegate 1008 is able to fire off HTTPS requests tothe GCM server. It should have API key to communicate with GCM andregistration id to send notifications to particular device through GCM.API key should be included in the header of POST requests.

The following table provides exemplary details for the mobile OSnotification cloud 1010:

GCM APNS WPNS Registration ID size Can grow up to 4 KB, 32 bytes as ofnow, but URI is used as ID, size no fix size can grow up to 4 K cannotexceeded 2055 bytes. Ports to open 5228, 5229, and 5230. TransmissionControl For notification to work GCM typically only Protocol (TCP) portcorrectly for Windows uses 5228, but it 5223 (used by devices Phone oriOS devices, sometimes uses 5229 to communicate to the firewall rulesmust and 5230. GCM doesn't APNs servers) allow port 443/TCP providespecific IPs. It TCP port 2195 (used inbound and outbound changes IPsfrequently. to send notifications to and port 5223/TCP the APNs)outbound. TCP port 2196 (used by the APNs feedback service) TCP Port 443(used as a fall back on Wi-Fi only, when devices are unable tocommunicate to APNs on port 5223) The APNs servers use load balancing.Devices will not always connect to the same public IP address fornotifications. The entire 17.0.0.0/8 address block is assigned to Apple,so it's best to allow this range in firewall settings.

Referring to FIG. 12, in an exemplary embodiment, a screen shotillustrates an exemplary out-of-band notification to a mobile device.Note, the out-of-band notification provides the end user information asto what was blocked and why as well as contact information if the userbelieves that the block was in error.

§ 11.0 Secure and Lightweight Tunnel

The advent of mobile applications has burgeoned forth numerouschallenges for network security systems, such as the cloud systems 100,500 and the distributed security cloud 552. The conventional proxy basedtraffic forwarding solutions fail to identify and tag traffic toappropriate users, devices and mobile applications. Further in mobileplatforms, forwarding all device traffic using a proxy is difficultbecause of limited system access. Also, enforcing app specific policies(such as allow/block, bandwidth control, etc.) is difficult for networksecurity systems, as apps usually do not have unique user agents ascompared to conventional browser based web surfing.

In various exemplary embodiments, the secure and lightweight trafficforwarding systems and methods include an agent app installed on themobile device 400. This agent app can be the same as the agent 1002. Theagent app works cooperatively with a secure cloud gateway, such as thecloud systems 100, 500, the distributed security cloud 552, the cloudsystem 904, etc., to listen for Web/DNS traffic to applyorganizationally defined policies per user and per device on alloutbound and inbound traffic, such as, for example, to block malware,block when request violates company security policy, etc. The agent appon the mobile device 400 opens local listening sockets, and reroutesoutgoing requests (HTTP and User Datagram Protocol (UDP)) to locallistening sockets, identify apps which originates those requests andthen forward requests to secure cloud gateway with pertinent user anddevice information and application identification (such as unique appname) attached to request. Based on the configuration, the secure cloudgateway applies policies and sends responses to the agent thattransduces the response back to the client app. In case of a remotepolicy violation, the agent app can receive an out of the bound end usernotification as described herein. In case of a local policy violation(e.g., 3G quota exceed), the agent app can block the requests and showlocally generated end user notifications. Such a traffic forwardingsolution is scalable to the BYOD (Bring your own device) model ofcomputing as well where only partial device or containerized traffic isforwarded to the secure web gateways.

Referring to FIG. 13, in an exemplary embodiment, a network diagramillustrates a secure and lightweight tunnel configuration 1200 between amobile device 400 and a cloud system 1202. The cloud system 1202 can beany of the cloud systems 100, 500, the distributed security cloud 552,the cloud system 904, etc., and is illustrated with two exemplary cloudnodes 502. The secure and lightweight tunnel configuration 1200 isconfigured to provide 1) user enrollment and device authorization; 2)device wide or containerized traffic forwarding (Web/DNS) to the cloudsystem 1202 with appropriate user, device and application levelinformation; 3) handling local policy configuration such as bandwidthcontrol; and 4) handling end user notifications locally generated for alocal device policy violation or remotely generated via a pushnotification cloud.

The secure and lightweight tunnel configuration 1200 includes a devicecontainer or selected apps 1210 on the mobile device 400 thatcommunicates traffic 1212 to IP tables 1214. The device 400 can use theIP tables 1214 to communicate the traffic 1212 to the cloud system 1202through a web proxy 1220 or DNS proxy 1222. For example, traffic 1224can include port 80, 443 traffic, i.e. HTTP or HTTPS traffic 1224, andtraffic 1226 can include port 53 traffic, i.e. DNS traffic 1226. The webproxy 1220 and the DNS proxy 1222 are processes or the like executed bythe mobile device 400 to realize the secure and lightweight tunnelconfiguration 1200.

For the HTTP or HTTPS traffic 1224, the web proxy 1220 transmits theHTTP connection information (e.g., connect to a destination 1228) alongwith app information (associated with the HTTP or HTTPS traffic 1224)and digest information to the cloud node 502 a (which can be aprocessing node 110 or the like) (step 1230). The cloud node 502, in thedistributed security system, can forward the HTTP or HTTPS traffic 1224if policy allows (step 1232) and enable establishment of a connectionwith the mobile device (step 1234).

For the DNS traffic 1226, the DNS proxy 1222 can either establish oralready have established a socket passing client certificate authorityinformation and device identification on a first DNS request (step1240). The DNS proxy 1222 transmits a DNS request from the DNS traffic1226 with app information and a unique request identifier to a cloudnode 502 b, which is acting to provide DNS augmented security (step1242). The cloud node 502 b queries a DNS server 1250 if policy allows(step 1252), and returns the DNS response, from the DNS server 1250,with the same unique request identifier (step 1254).

Referring to FIG. 14, in an exemplary embodiment, a screen diagramillustrates an exemplary UI for the secure and lightweight tunnelconfiguration 1200. Here, an administrator can configure policies forthe mobile devices 400, such as policies including, without limitation,allowing or blocking transactions from apps that falls in certaincategories like Malware, location, information leak, etc.; configuringSSL traffic interception for mobile devices; configuring out of boundend user notifications for mobile traffic; configuring 3G monthly quotafor mobile devices; etc.

Referring to FIG. 15, in an exemplary embodiment, a flow diagramillustrates a policy configuration sequence system 1300 and method 1302.The system 1300 is similar to the notification system 1000 and includesan admin 1304, a UI 1306, a central authority (CA) 1004, a cloud node(CN) 1006, and a mobile operating system (OS) notification cloud 1010.Collectively, the devices 1004, 1006, 1306 can be part of thedistributed security system 100, the cloud system 500, the distributedsecurity cloud 552, the cloud system 904, the cloud system 1202, etc.

The policy configuration sequence system 1300 and method 1302illustrates how the admin 1304 interacts with the secure and lightweighttunnel configuration 1200 to set policy. Note, the secure andlightweight tunnel configuration 1200 is described in FIG. 16 withreference to the user and the mobile device 400. The secure andlightweight tunnel configuration 1200 is configured to provide a secureand lightweight tunnel for external communications from the mobiledevice 400 through the cloud system 1202.

The admin 1304 can define or update a configuration policy through theUI 1306 (step 1312). The configuration policy can be for a user or groupof users. Once defined, the UI 1306 fetches device identifiers from theCA 1004 for users impacted by the configuration policy (step 1314), andsends updated policy notifications, based on the configuration policy,through the mobile OS notification cloud 1010 (step 1316). The mobile OSnotification cloud 1010 is configured to push the updated policynotifications to the associated devices 400, through the cloud node 1006and the secure and lightweight tunnel configuration 1200 (step 1318).

Referring to FIG. 16, in an exemplary embodiment, a flow diagramillustrates a user registration and notification system 1400 and method1402, with the secure and lightweight tunnel configuration 1200. Note,the user registration and notification system 1400 and method 1402 issimilar to the notification system 1000, with the agent 1002 beingreplaced with a secure and lightweight tunnel configuration app 1404.The user registration and notification system 1400 includes the secureand lightweight tunnel configuration app 1400 at the mobile device 400,the central authority (CA) 1004, the delegate 1008, and the mobileoperating system (OS) notification cloud 1010.

Note, the configuration app 1404 may be combined with the agent 1002.The configuration app 1404 is a software program or app that isinstalled and operated on the mobile device 400. The configuration app1404 can have various functionality such as authentication with thesystems 100, 500, end user notification (EUN), and the like.Additionally, the configuration app 1404 can be distributed or installedthrough mobile OS-specific mechanisms such as Google Play (AndroidMarketplace), Apple App Store, Windows Marketplace, etc. The CA 1004 isa central authority (CA) server which can be used by the systems 100,500 to track users. The CN 1006 can be the processing node 110 in thesystem 100 or the cloud node 502 in the system 500.

The method 1402 includes installing the configuration app 1404, such asan app on the mobile device 400 (step 1041). This can be done via themobile OS-specific mechanisms or the like. An administrator c apreconfigured email to the mobile device 400 (step 1412) and the userexecutes a preconfigured link or the like in the email on the mobiledevice 400 (step 1413). These steps configure the configuration app 1404with the specific user and associated policy in the system 100, 500.Once configured and operating, the user can perform authentication suchas with the configuration app 1404 through the cloud system 1202 (step1414). The authentication can be anything known in the art, e.g. User IDand password, etc. The cloud system 1202 responds with a cookie (ifsuccessful) or error (if not successful) (step 1415). If theauthentication is successful, a device posture is sent to the CA 1004 toupdate the last User ID for the mobile device 400 (step 1416). This isto create a User ID to IP binding as is described herein such that thesystem 100, 500 can know who is using the mobile device 400.

The method 1402 can include initiating a mobile app transaction, throughthe secure and lightweight tunnel configuration 1200 (step 1417). If themobile app transaction complies with relevant policy, does not containmalware, etc., the method 1402 would end here and the mobile apptransaction would be successful. If the mobile app transaction is notsuccessful, e.g., blocked, cautioned, etc., the cloud system 1202 cansend a notification request URL to the delegate 1008 (step 1418). Thedelegate 1008 sends the request to the mobile OS notification cloud 1010(step 1419), and the message can be delivered to the mobile device outof band (step 1420).

§ 11.1 Traffic Rerouting Method—Secure and Lightweight Tunnel

Referring to FIG. 17, in an exemplary embodiment, a flowchartillustrates a traffic rerouting method 1500 for the secure andlightweight tunnel configuration 1200. After registering the mobiledevice 400 with the cloud system 1202, the agent 1002 or theconfiguration app 1404 configures traffic redirection policies toforward traffic from the mobile device 400 to the cloud system 1202. Theagent 1002 or the configuration app 1404 opens a listening socket andreroutes desired traffic to that socket. The agent 1002 or theconfiguration app 1404 opens a TCP listening socket for web traffic andUDP listening socket for DNS traffic (step 1502). The agent 1002 or theconfiguration app 1404 configures policy to redirect outgoing Web andDNS traffic (from all apps except the agent 1002 or the configurationapp 1404) to the local TCP and UDP ports (step 1504).

For the traffic redirection, two approaches can be used—an IP tables1214 firewall rules based approach or a tunnel interface approach. Forthe IP tables 1214 firewall rules based approach, the agent 1002 or theconfiguration app 1404 will configure firewall rules to reroute desiredtraffic to the local listening socket, TCP listening socket for webtraffic and UDP listening socket for DNS traffic. For example, forWeb/HTTP tunneling, the agent 1002 or the configuration app 1404configures a forwarding rule to reroute traffic destined to port 80 and443 to 127.0.0.1:zz where zz is agent's listening TCP socket port. ForDNS tunneling, the agent 1002 or the configuration app 1404 configures aforwarding rule to reroute traffic destined to port 53 to 127.0.0.1:zzwhere zz is agent's listening UDP socket port.

Referring to FIG. 18, in an exemplary embodiment, a flowchartillustrates a tunnel interface approach 1550 for the traffic redirectionin the traffic rerouting method 1500. The agent 1002 or theconfiguration app 1404 will setup a new tunnel interface (ex. tun0) andwith a default route (0.0.0.0) set for that interface (step 1552). Theagent 1002 or the configuration app 1404 reads an IP packet from theinterface (step 1554). The agent 1002 or the configuration app 1404swaps the source and destination IP addresses (step 1556). If thepacket's source port is not equal to the agent's listening socket port(step 1558), the agent 1002 or the configuration app 1404 replaces thepacket's destination port with the listening socket port and a key-valueentry <source port, destination port> is added to a mapping table (step1560). If the packet's source port is equal to the agent's listeningsocket port (step 1558), the agent 1002 or the configuration app 1404gets the value corresponding to the packet destination port in themapping table and replaces the packet source port with this value (step1562). Subsequent to the steps 1560 m 1562, the agent 1002 or theconfiguration app 1404 computes IP and TCP/UDP checksums and overwritethe original checksums in the packet (step 1564) and writes the modifiedpacket to the interface (step 1566). The steps 1556-1566 can beperformed for every packet read from the interface.

For example, let x.x.x.x be an IP address of a tunnel interface and zzbe a local listening socket port.

Original Packet Modified Packet Request packet from client app: SRC:y.y.y.y:xx DEST: x.x.x.x:zz SRC: x.x.x.x:xx DEST: y.y.y.y:yy Entry addedto mapping table: <xx,yy> Response packet from Entry fetched frommapping listening socket: table for key xx is yy SRC: x.x.x.x:zz DEST:y.y.y.y:xx SRC: y.y.y.y:yy DEST: x.x.x.x:xx

§ 11.2 Reading Traffic and Applying Local Policies—Secure andLightweight Tunnel

Referring to FIG. 19, in an exemplary embodiment, a flowchartillustrates a local policy method 1600, with the secure and lightweighttunnel configuration 1200. The local policy method 1600 can beimplemented via the agent 1002 or the configuration app 1404 operatingat the mobile device 400. When any mobile device app tries to make Webor DNS requests, the agent's TCP and UDP listening sockets will receivethe corresponding Web and DNS requests (step 1602). On receiving arequest, the agent 1002 or the configuration app 1404 reads socketparameters i.e. local and remote IP/port of socket and unique identifier(UID) of process to which the socket belongs, and the agent 1002 or theconfiguration app 1404 then derives app package name from the app UID(step 1604). For non-Web/DNS traffic (step 1606), the agent 1002 or theconfiguration app 1404 directly relays the request out to the Internet(step 16108). For Web/DNS traffic (step 1606), the agent 1002 or theconfiguration app 1404 first applies local policies (step 1610). Forexample, a particular app is not allowed to browse due to a bandwidthquota limit. If the request is not allowed based on the local policies(step 1612), then there is a local block/traffic drop at the mobiledevice (step 1614). Otherwise, the agent 1002 or the configuration app1404 forwards the request to the secure cloud to apply remote policies(step 1616).

After a request passes local policies, the agent 1002 or theconfiguration app 1404 forwards request to cloud to apply remotepolicies. The forwarding request step can be for a Web/HTTP request or aDNS request. For a Web/HTTP request, the agent 1002 or the configurationapp 1404 opens and outgoing socket to the secure cloud gateway for eachaccepted local socket. The agent 1002 or the configuration app 1404writes HTTP Connect destination_IP:Port to the outgoing socket andpasses app identification (app unique package name, app version, OSversion, device model, agent app version, etc.) in a User-Agent headerand passes device login credentials for digest authentication with thesecure cloud gateway. For example, a request could be: Example request:

CONNECT 68.178.230.53:80 HTTP/1.1 Host: 68.178.230.53:80User-Agent: com.sec.android.app.sbrowser/1528 Android/4.4.2SAMSUNG-GT-I9505 ZTunnel/1.0 Connection: Keep-Alive Proxy-Authorization:Digest .........

The secure cloud accepts the request if digest credentials are valid andestablishes the tunnel. The agent 1002 or the configuration app 1404, onreceiving success, reads request data from an accepted client socket andwrites that data to the outgoing socket. The secure cloud reads apprequest, applies policies and sends response back. The agent 1002 or theconfiguration app 1404 reads response data from the tunnel and writesthe data back to client socket.

For a DNS request, the agent 1002 or the configuration app 1404 opens anoutgoing TLS socket/tunnel with a secure cloud DNS service passingclient certificate, device IS, authentication information, securitylevel, etc. The agent 1002 or the configuration app 140 accepts DNSrequests on the local listening socket. On receiving a DNS request, itaccepts request and reads DNS packet data, and the makes a custom DNSrequest by assigning a unique ID to the original DNS request, addingapplication information to the request (app unique package name, appversion, etc.). The agent adds a mapping table entry <unique req ID,client socket> and then writes the custom request to the outgoingtunnel. The secure cloud reads request, triggers per user/app policies,and sends a DNS response back with same req ID. If a block is trigger,the secure cloud sends its own webserver IP, else it resolves the DNSrequest and sends the actual IP. The agent reads the response from theoutgoing tunnel, gets an entry from mapping table corresponding tounique req ID and sends the DNS response back to client app. The agentalso parses the DNS response and in case of block response shows locallygenerated notification as explained below.

Referring to FIGS. 20 and 21, in an exemplary embodiment, mobile screenshots illustrate a locally triggered end user notification (FIG. 20) anda remotely triggered end user notification (FIG. 21). If a request wasblocked due to local policy such as due to bandwidth quota limit, theagent shows locally generated notification, such as illustrated, forexample, in FIG. 20. If the request was blocked by the secure cloud, itsends out of bound notification to mobile device i.e. it sendsnotification to delegate server which sends it to appropriate server(APNS/GCM) which then sends Push notification to device, such asillustrated in FIG. 21.

Referring to FIG. 22, in an exemplary embodiment, a mobile screen shotillustrates a locally generated DNS block notification. If a request wasblocked, the secure cloud resolves DNS request to the IP of its own webserver (block IP). The agent checks for response IP in the DNS response.If block IP is returned, the agent generates local notification data andshows End user notification UI, such as shown in FIG. 22.

It will be appreciated that some exemplary embodiments described hereinmay include one or more generic or specialized processors (“one or moreprocessors”) such as microprocessors, digital signal processors,customized processors, and field programmable gate arrays (FPGAs) andunique stored program instructions (including both software andfirmware) that control the one or more processors to implement, inconjunction with certain non-processor circuits, some, most, or all ofthe functions of the methods and/or systems described herein.Alternatively, some or all functions may be implemented by a statemachine that has no stored program instructions, or in one or moreapplication specific integrated circuits (ASICs), in which each functionor some combinations of certain of the functions are implemented ascustom logic. Of course, a combination of the aforementioned approachesmay be used. Moreover, some exemplary embodiments may be implemented asa non-transitory computer-readable storage medium having computerreadable code stored thereon for programming a computer, server,appliance, device, etc. each of which may include a processor to performmethods as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, an optical storage device, a magnetic storage device, a ROM(Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM(Erasable Programmable Read Only Memory), an EEPROM (ElectricallyErasable Programmable Read Only Memory), Flash memory, and the like.When stored in the non-transitory computer readable medium, software caninclude instructions executable by a processor that, in response to suchexecution, cause a processor or any other circuitry to perform a set ofoperations, steps, methods, processes, algorithms, etc.

Although the present disclosure has been illustrated and describedherein with reference to preferred embodiments and specific examplesthereof, it will be readily apparent to those of ordinary skill in theart that other embodiments and examples may perform similar functionsand/or achieve like results. All such equivalent embodiments andexamples are within the spirit and scope of the present disclosure, arecontemplated thereby, and are intended to be covered by the followingclaims.

What is claimed is:
 1. A cloud node in a cloud system, the cloud nodecomprising: a network interface communicatively coupled to a network, aprocessor communicatively coupled to the network interface, and memorystoring instructions that when executed cause the processor to:receiving traffic from a mobile device based on forwarding from locallistening sockets on the mobile device, wherein the local listeningsockets are opened on the mobile device and the traffic is redirectedfrom applications on the mobile device to the local listening socketsand forwarded to the cloud node with additional information related toan associated application on the mobile device; and applying one or moreremote policies in the cloud node to the traffic based in part on theadditional information.
 2. The cloud node of claim 1, wherein the locallistening sockets are a Transmission Control Protocol (TCP) listeningsocket for Web traffic and a User Datagram Protocol (UDP) listeningsocket for Domain Name System (DNS) traffic.
 3. The cloud node of claim1, wherein the additional information comprises any of applicationunique package name, application version, operating system version,device model, and agent version.
 4. The cloud node of claim 1, whereinthe memory storing instructions that when executed further cause theprocessor to: enroll a user of the mobile device in the cloud system andauthorize the mobile device in the cloud system.
 5. The cloud node ofclaim 1, wherein the memory storing instructions that when executedfurther cause the processor to: responsive to a violation of the one ormore remote policies, provide an end user notification to the mobiledevice via a push notification to the mobile device.
 6. The cloud nodeof claim 5, wherein the push notification is via a mobile operatingsystem notification cloud.
 7. The cloud node of claim 1, wherein thememory storing instructions that when executed further cause theprocessor to: responsive to a violation of the one or more remotepolicies, block the traffic in the cloud node and provide an end usernotification to the mobile device.
 8. The cloud node of claim 1, whereinthe one or more remote policies comprise allowing or blockingtransactions from one or more applications on the mobile device.
 9. Thecloud node of claim 8, wherein the one or more applications are allowedor block based on one or more of malware detection, location, andsusceptibility to information leakage.
 10. The cloud node of claim 1,wherein the mobile device comprises a user device configured with theone or more remote policies for an organization associated with a userof the mobile device.
 11. A cloud method in a node in a cloud system,the cloud method comprising: receiving traffic from a mobile devicebased on forwarding from local listening sockets on the mobile device,wherein the local listening sockets are opened on the mobile device andthe traffic is redirected from applications on the mobile device to thelocal listening sockets and forwarded to the cloud node with additionalinformation related to an associated application on the mobile device;and applying one or more remote policies in the cloud node to thetraffic based in part on the additional information.
 12. The cloudmethod of claim 11, wherein the local listening sockets are aTransmission Control Protocol (TCP) listening socket for Web traffic anda User Datagram Protocol (UDP) listening socket for Domain Name System(DNS) traffic.
 13. The cloud method of claim 11, wherein the additionalinformation comprises any of application unique package name,application version, operating system version, device model, and agentversion.
 14. The cloud method of claim 11, further comprising: enrollinga user of the mobile device in the cloud system and authorizing themobile device in the cloud system.
 15. The cloud method of claim 11,further comprising: responsive to a violation of the one or more remotepolicies, providing an end user notification to the mobile device via apush notification to the mobile device.
 16. The cloud method of claim15, wherein the push notification is via a mobile operating systemnotification cloud.
 17. The cloud method of claim 11, furthercomprising: responsive to a violation of the one or more remotepolicies, blocking the traffic in the cloud node and providing an enduser notification to the mobile device.
 18. The cloud method of claim11, wherein the one or more remote policies comprise allowing orblocking transactions from one or more applications on the mobiledevice.
 19. The cloud method of claim 18, wherein the one or moreapplications are allowed or block based on one or more of malwaredetection, location, and susceptibility to information leakage.
 20. Anon-transitory computer readable medium comprising instructions thatwhen executed cause a processor in a cloud node to: receive traffic froma mobile device based on forwarding from local listening sockets on themobile device, wherein the local listening sockets are opened on themobile device and the traffic is redirected from applications on themobile device to the local listening sockets and forwarded to the cloudnode with additional information related to an associated application onthe mobile device; and apply one or more remote policies in the cloudnode to the traffic based in part on the additional information.